Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83df704383495ec8816b0ea9966e92e57a793a93b93b248ac1b6a372dc6b63ad

Tx prefix hash: 32678b6169f33820a483c6d58df926ddb292acd35ed29af832e3744c900ad0af
Tx public key: ecaaccb71b2365f06b3535f24c21d58d914749ebccae4a2cf6adbef851248dc2
Timestamp: 1715150942 Timestamp [UCT]: 2024-05-08 06:49:02 Age [y:d:h:m:s]: 01:007:22:00:06
Block: 1017360 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 266573 RingCT/type: yes/0
Extra: 01ecaaccb71b2365f06b3535f24c21d58d914749ebccae4a2cf6adbef851248dc20211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 872007e3600b896a2b2b4e26d08b97dc51a5d6c0a409f232a4a313b6497b8380 0.600000000000 1481135 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": 1017370, "vin": [ { "gen": { "height": 1017360 } } ], "vout": [ { "amount": 600000000, "target": { "key": "872007e3600b896a2b2b4e26d08b97dc51a5d6c0a409f232a4a313b6497b8380" } } ], "extra": [ 1, 236, 170, 204, 183, 27, 35, 101, 240, 107, 53, 53, 242, 76, 33, 213, 141, 145, 71, 73, 235, 204, 174, 74, 44, 246, 173, 190, 248, 81, 36, 141, 194, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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