Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d4a893107bdbe9ced7228e81015eb11109a4e16d214fe194e21e888fe2eb0ab

Tx prefix hash: 3b4eeac803dae8cd0ac8d78eb5239bc9395d0c51426efd244ea9438b277bcd03
Tx public key: 807e48ef4e8d4a7b968d0432999a4bcdce7e66b89fc64b8ec6dc94ab42a0940e
Timestamp: 1649721023 Timestamp [UCT]: 2022-04-11 23:50:23 Age [y:d:h:m:s]: 02:338:15:02:31
Block: 478222 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 761693 RingCT/type: yes/0
Extra: 01807e48ef4e8d4a7b968d0432999a4bcdce7e66b89fc64b8ec6dc94ab42a0940e02110000000dc9067537000000000000000000

1 output(s) for total of 15.977718060000 dcy

stealth address amount amount idx
00: 7b7eba3d44a58e1ef9a5586b64922bd3318da2cb1d057b88bd5ad906b79329aa 15.977718060000 898957 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": 478232, "vin": [ { "gen": { "height": 478222 } } ], "vout": [ { "amount": 15977718060, "target": { "key": "7b7eba3d44a58e1ef9a5586b64922bd3318da2cb1d057b88bd5ad906b79329aa" } } ], "extra": [ 1, 128, 126, 72, 239, 78, 141, 74, 123, 150, 141, 4, 50, 153, 154, 75, 205, 206, 126, 102, 184, 159, 198, 75, 142, 198, 220, 148, 171, 66, 160, 148, 14, 2, 17, 0, 0, 0, 13, 201, 6, 117, 55, 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