Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eaa3a21e8c76295c3cb878446b125d3642c63dc6fbc3ce079d788d98f101ed34

Tx prefix hash: 1ff0e631e6e41119195ffea644e9db7cafcceea0c493ef7bedd7a434465a6ebd
Tx public key: 37b8f69d4421d5095546f9e5834b4e7f272d5f4d87c36d5605704929fd159e10
Timestamp: 1704316892 Timestamp [UCT]: 2024-01-03 21:21:32 Age [y:d:h:m:s]: 01:133:22:53:28
Block: 927547 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356848 RingCT/type: yes/0
Extra: 0137b8f69d4421d5095546f9e5834b4e7f272d5f4d87c36d5605704929fd159e10021100000001c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d954691cbc29ee801a3d06d90b1dc24ced629ea8d725aab1357ebf95789b293f 0.600000000000 1385383 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": 927557, "vin": [ { "gen": { "height": 927547 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d954691cbc29ee801a3d06d90b1dc24ced629ea8d725aab1357ebf95789b293f" } } ], "extra": [ 1, 55, 184, 246, 157, 68, 33, 213, 9, 85, 70, 249, 229, 131, 75, 78, 127, 39, 45, 95, 77, 135, 195, 109, 86, 5, 112, 73, 41, 253, 21, 158, 16, 2, 17, 0, 0, 0, 1, 197, 69, 41, 96, 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