Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5818806475558c009d8840de03297eb3088c71e0e68ed985f90e3cdd6c18b33f

Tx prefix hash: 1bc153dd9fd56ae650644f6508b7ba4006ecad63e19ad8f8e96055d982208897
Tx public key: 6f461ee54768f9e8dd44b5c037df340de06f9aeaa58d4bb1404e35bbf417d4c9
Timestamp: 1734753549 Timestamp [UCT]: 2024-12-21 03:59:09 Age [y:d:h:m:s]: 00:018:18:08:48
Block: 1179781 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13381 RingCT/type: yes/0
Extra: 016f461ee54768f9e8dd44b5c037df340de06f9aeaa58d4bb1404e35bbf417d4c90211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 542c373778de4d50ffd936309b529e952f8dd2abb17ce410eccb2e0a69cd7c7e 0.600000000000 1666180 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": 1179791, "vin": [ { "gen": { "height": 1179781 } } ], "vout": [ { "amount": 600000000, "target": { "key": "542c373778de4d50ffd936309b529e952f8dd2abb17ce410eccb2e0a69cd7c7e" } } ], "extra": [ 1, 111, 70, 30, 229, 71, 104, 249, 232, 221, 68, 181, 192, 55, 223, 52, 13, 224, 111, 154, 234, 165, 141, 75, 177, 64, 78, 53, 187, 244, 23, 212, 201, 2, 17, 0, 0, 0, 2, 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