Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 997137e7b49c6f5dd34f328d69afc8b19ea40d31d040a64484ca40192fa5a478

Tx prefix hash: 7bcbfafe078dfa3d08ee71f8a34b4d0fdaaf21cbb4355bcb44f0df926fee4606
Tx public key: 9ef515a79f74fe245b84f5f4afb251cc024cccfa119e40d38d82164a402c00b1
Timestamp: 1734345207 Timestamp [UCT]: 2024-12-16 10:33:27 Age [y:d:h:m:s]: 00:093:09:20:19
Block: 1176391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66533 RingCT/type: yes/0
Extra: 019ef515a79f74fe245b84f5f4afb251cc024cccfa119e40d38d82164a402c00b1021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 735144293fba6cb879a76178c13e4217d61bebc8906ca3b078c3723ef3addc50 0.600000000000 1662722 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": 1176401, "vin": [ { "gen": { "height": 1176391 } } ], "vout": [ { "amount": 600000000, "target": { "key": "735144293fba6cb879a76178c13e4217d61bebc8906ca3b078c3723ef3addc50" } } ], "extra": [ 1, 158, 245, 21, 167, 159, 116, 254, 36, 91, 132, 245, 244, 175, 178, 81, 204, 2, 76, 204, 250, 17, 158, 64, 211, 141, 130, 22, 74, 64, 44, 0, 177, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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