Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 576c7b6b8847b21564f3b617555f8132608cb9b0d9468b7bf2bfa423e0f19453

Tx prefix hash: 21862a53d424a6749c69ddb7b30dcd68f6b77f59d55eaf1c3ff44a2181b87b1a
Tx public key: df5638c24bb33f10800afba82c4448311a078ae96ece22baf625698fc5c4f1a8
Timestamp: 1737167933 Timestamp [UCT]: 2025-01-18 02:38:53 Age [y:d:h:m:s]: 00:150:20:18:37
Block: 1199734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107512 RingCT/type: yes/0
Extra: 01df5638c24bb33f10800afba82c4448311a078ae96ece22baf625698fc5c4f1a80211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a3e2f70682dd02ca19d93e8be0493c1aad4b13514a6a1156b210721838a5af8 0.600000000000 1686367 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": 1199744, "vin": [ { "gen": { "height": 1199734 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a3e2f70682dd02ca19d93e8be0493c1aad4b13514a6a1156b210721838a5af8" } } ], "extra": [ 1, 223, 86, 56, 194, 75, 179, 63, 16, 128, 10, 251, 168, 44, 68, 72, 49, 26, 7, 138, 233, 110, 206, 34, 186, 246, 37, 105, 143, 197, 196, 241, 168, 2, 17, 0, 0, 0, 4, 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