Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a48ec7bf051de9576ad7479103133257e609a5d169ce10ce2cd3b4d5b2c16b5a

Tx prefix hash: 10a172156141ecb93f1160dc542b2ddf9fb2eb3a4d72810600cf30cbb4c5f3be
Tx public key: 5e954e2db5a994037a74916e3db7fe91bcc79ddf9dc4de949db25bc6e4f82ce7
Timestamp: 1738184131 Timestamp [UCT]: 2025-01-29 20:55:31 Age [y:d:h:m:s]: 00:295:02:26:41
Block: 1207900 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208656 RingCT/type: yes/0
Extra: 015e954e2db5a994037a74916e3db7fe91bcc79ddf9dc4de949db25bc6e4f82ce70211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c3e11bb8e1840f4c00af5b1cd6adebe18e9e4e7804e1ff44e90d968efe46f32 0.600000000000 1694627 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": 1207910, "vin": [ { "gen": { "height": 1207900 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c3e11bb8e1840f4c00af5b1cd6adebe18e9e4e7804e1ff44e90d968efe46f32" } } ], "extra": [ 1, 94, 149, 78, 45, 181, 169, 148, 3, 122, 116, 145, 110, 61, 183, 254, 145, 188, 199, 157, 223, 157, 196, 222, 148, 157, 178, 91, 198, 228, 248, 44, 231, 2, 17, 0, 0, 0, 3, 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