Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b53bfa0614d6defbca6337951010c091a6ea37d032167003d52ed211190b4df

Tx prefix hash: b56b9bb9b9ede6d2644238ff30458592e649b3b7b019a5a982a37feae8a33ce7
Tx public key: 191d7eef7cba3dabe9c9135aaa7a076cce1928f589fb45a884da567e8e32b98e
Timestamp: 1714454113 Timestamp [UCT]: 2024-04-30 05:15:13 Age [y:d:h:m:s]: 01:028:22:11:20
Block: 1011575 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281634 RingCT/type: yes/0
Extra: 01191d7eef7cba3dabe9c9135aaa7a076cce1928f589fb45a884da567e8e32b98e0211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9406b655ccb5570b2232055f9175c4a8519311a3ba1c3fe40a5f96a161bc50d 0.600000000000 1473841 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": 1011585, "vin": [ { "gen": { "height": 1011575 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9406b655ccb5570b2232055f9175c4a8519311a3ba1c3fe40a5f96a161bc50d" } } ], "extra": [ 1, 25, 29, 126, 239, 124, 186, 61, 171, 233, 201, 19, 90, 170, 122, 7, 108, 206, 25, 40, 245, 137, 251, 69, 168, 132, 218, 86, 126, 142, 50, 185, 142, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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