Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d647229e22426819285b87c55e6d7e2f13fd603f0d99f652f2eddb546c115d8f

Tx prefix hash: 652a8a26d7832805b3cff54057f886a3ca49d1e8ebcb2fd2c915b2c58145558d
Tx public key: b223835ec55e83addf2dc67ad09f89373308ce6f8d8106eb377a1bcac4da764e
Timestamp: 1686064405 Timestamp [UCT]: 2023-06-06 15:13:25 Age [y:d:h:m:s]: 01:352:22:17:19
Block: 776462 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 513470 RingCT/type: yes/0
Extra: 01b223835ec55e83addf2dc67ad09f89373308ce6f8d8106eb377a1bcac4da764e02110000000575e3f0e9000000000000000000

1 output(s) for total of 1.641569346000 dcy

stealth address amount amount idx
00: ff2238c66c8b593ce9ef23af867500cd7db8e652ba23643ef157d7c468fe9f0b 1.641569346000 1226017 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": 776472, "vin": [ { "gen": { "height": 776462 } } ], "vout": [ { "amount": 1641569346, "target": { "key": "ff2238c66c8b593ce9ef23af867500cd7db8e652ba23643ef157d7c468fe9f0b" } } ], "extra": [ 1, 178, 35, 131, 94, 197, 94, 131, 173, 223, 45, 198, 122, 208, 159, 137, 55, 51, 8, 206, 111, 141, 129, 6, 235, 55, 122, 27, 202, 196, 218, 118, 78, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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