Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0598cf26a51c2c1ce7191d5025d1ba73189ac475e98f8cae4363e79b8d0f30e

Tx prefix hash: 2e021b37e62831cf388ab33caa4751a32c5847eab1f85d1f92300a46a03e5780
Tx public key: b31564dafea085b1639bd2a5913c269aed1bf78cbc0e0adff91dd4fb1080bfc6
Timestamp: 1643325046 Timestamp [UCT]: 2022-01-27 23:10:46 Age [y:d:h:m:s]: 02:307:19:13:19
Block: 426660 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 738498 RingCT/type: yes/0
Extra: 01b31564dafea085b1639bd2a5913c269aed1bf78cbc0e0adff91dd4fb1080bfc6021100000009bf0a3242000000000000000000

1 output(s) for total of 23.675470474000 dcy

stealth address amount amount idx
00: 3c3230499169eb192684e0d03d51691c9295961d20f81722a85d7170de8a4177 23.675470474000 835521 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": 426670, "vin": [ { "gen": { "height": 426660 } } ], "vout": [ { "amount": 23675470474, "target": { "key": "3c3230499169eb192684e0d03d51691c9295961d20f81722a85d7170de8a4177" } } ], "extra": [ 1, 179, 21, 100, 218, 254, 160, 133, 177, 99, 155, 210, 165, 145, 60, 38, 154, 237, 27, 247, 140, 188, 14, 10, 223, 249, 29, 212, 251, 16, 128, 191, 198, 2, 17, 0, 0, 0, 9, 191, 10, 50, 66, 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