Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd5bd71566feafb7b6345fee88c13bd495d1908dcca01f4d15fc81fe9352791c

Tx prefix hash: 61749b2eff99f6297b57d185f31d29e7134fbccf79bb5aa0d66851cbed1328d6
Tx public key: 7322a7c07d833364046c290b9c765ca2c9ee978f7e9ce9bf4601652a9aee77ef
Timestamp: 1626756854 Timestamp [UCT]: 2021-07-20 04:54:14 Age [y:d:h:m:s]: 04:110:17:33:24
Block: 297365 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1109140 RingCT/type: yes/0
Extra: 017322a7c07d833364046c290b9c765ca2c9ee978f7e9ce9bf4601652a9aee77ef02110000001cc97064b9000000000000000000

1 output(s) for total of 63.490216392000 dcy

stealth address amount amount idx
00: 7905c745e1b55a78fc047a38b8f0e00caa37fa61a8a41ad5777e2da4edc48d8d 63.490216392000 622377 of 0

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": 297375, "vin": [ { "gen": { "height": 297365 } } ], "vout": [ { "amount": 63490216392, "target": { "key": "7905c745e1b55a78fc047a38b8f0e00caa37fa61a8a41ad5777e2da4edc48d8d" } } ], "extra": [ 1, 115, 34, 167, 192, 125, 131, 51, 100, 4, 108, 41, 11, 156, 118, 92, 162, 201, 238, 151, 143, 126, 156, 233, 191, 70, 1, 101, 42, 154, 238, 119, 239, 2, 17, 0, 0, 0, 28, 201, 112, 100, 185, 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