Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef30553fc64bf6945fa340f47cf103fa035b75d303971424d3f1edaf10d972ee

Tx prefix hash: 7d3418450bf022e4c716971141464fe0f51cb93ef16c9ed450d9c08eccef1085
Tx public key: fe0f5c44050a317bf1ce3d18f380a21845b789a81b39298c3b5e5d21e943a7a2
Timestamp: 1734052219 Timestamp [UCT]: 2024-12-13 01:10:19 Age [y:d:h:m:s]: 00:187:19:10:04
Block: 1173966 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133916 RingCT/type: yes/0
Extra: 01fe0f5c44050a317bf1ce3d18f380a21845b789a81b39298c3b5e5d21e943a7a20211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9fb07c5368c285a201611e9662927ef1c37c9fc05d3a1052d5c966d9f1d8d62e 0.600000000000 1660059 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": 1173976, "vin": [ { "gen": { "height": 1173966 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9fb07c5368c285a201611e9662927ef1c37c9fc05d3a1052d5c966d9f1d8d62e" } } ], "extra": [ 1, 254, 15, 92, 68, 5, 10, 49, 123, 241, 206, 61, 24, 243, 128, 162, 24, 69, 183, 137, 168, 27, 57, 41, 140, 59, 94, 93, 33, 233, 67, 167, 162, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 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