Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 4a4e248fc2848801ba61417931911bc90908ab61bc14bd7eb7f8bdfcc38f1267

Tx prefix hash: 78e73a5cf0b82372bda196eb58340c0d0426c9c179f2938d43d63a76d043cc7c
Tx public key: 42b4cba185ed3b4a1b129b4ea5f8d6472dbe70b22a6c2b6599893ebe381f768b
Timestamp: 1711617845 Timestamp [UCT]: 2024-03-28 09:24:05 Age [y:d:h:m:s]: 01:020:08:30:38
Block: 988076 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275499 RingCT/type: yes/0
Extra: 0142b4cba185ed3b4a1b129b4ea5f8d6472dbe70b22a6c2b6599893ebe381f768b02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38e4aec813aa9cedc2cdde9dff385fc45e81c535d355ad53cbfabc2b52f18c91 0.600000000000 1448337 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 988086, "vin": [ { "gen": { "height": 988076 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38e4aec813aa9cedc2cdde9dff385fc45e81c535d355ad53cbfabc2b52f18c91" } } ], "extra": [ 1, 66, 180, 203, 161, 133, 237, 59, 74, 27, 18, 155, 78, 165, 248, 214, 71, 45, 190, 112, 178, 42, 108, 43, 101, 153, 137, 62, 190, 56, 31, 118, 139, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8