Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 060d0555b388094ebf450165f2a57ea42ddaa140f85f7a6de528b9fa08f2b2ee

Tx prefix hash: 8e649164a6fd7e47374218a2a175c20eb17f4b2617733c9ac923990f2bdfe9df
Tx public key: 788b3ed107e701f11fe308e1a00ce9210b5532c06f520963f9c9a036d03da710
Timestamp: 1712653953 Timestamp [UCT]: 2024-04-09 09:12:33 Age [y:d:h:m:s]: 01:041:05:46:38
Block: 996629 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290479 RingCT/type: yes/0
Extra: 01788b3ed107e701f11fe308e1a00ce9210b5532c06f520963f9c9a036d03da7100211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6871a727b73ad86c82e9e08346373b69afa7df64bbdc880d0e91b884d170e7c1 0.600000000000 1457053 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": 996639, "vin": [ { "gen": { "height": 996629 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6871a727b73ad86c82e9e08346373b69afa7df64bbdc880d0e91b884d170e7c1" } } ], "extra": [ 1, 120, 139, 62, 209, 7, 231, 1, 241, 31, 227, 8, 225, 160, 12, 233, 33, 11, 85, 50, 192, 111, 82, 9, 99, 249, 201, 160, 54, 208, 61, 167, 16, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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