Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54da50d6f32828539b97e3d7f6161e4466a7343d5cb91b2f8912a67a1a2c5854

Tx prefix hash: a6753977ff1f6d71e2d5ef4cbd28a7d87f2edac1afaa3a62faff57952d1b69d2
Tx public key: e533aaa72b6c6d1d98fd5484be1c26f6101d7e6f1d9fed849f816dcac076cd78
Timestamp: 1708262722 Timestamp [UCT]: 2024-02-18 13:25:22 Age [y:d:h:m:s]: 01:261:16:16:44
Block: 960250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 445751 RingCT/type: yes/0
Extra: 01e533aaa72b6c6d1d98fd5484be1c26f6101d7e6f1d9fed849f816dcac076cd7802110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4cd37cd3f2b737446e6b75d0d3b65536ff190f48507809c59384e92f11cb2e32 0.600000000000 1419813 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": 960260, "vin": [ { "gen": { "height": 960250 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4cd37cd3f2b737446e6b75d0d3b65536ff190f48507809c59384e92f11cb2e32" } } ], "extra": [ 1, 229, 51, 170, 167, 43, 108, 109, 29, 152, 253, 84, 132, 190, 28, 38, 246, 16, 29, 126, 111, 29, 159, 237, 132, 159, 129, 109, 202, 192, 118, 205, 120, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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