Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab99c88674944400c6f09e999713f367a25910fb171f9b6c0a41ddec3f40ab9f

Tx prefix hash: 0bd7a358ded20dde72af4afeac1021ccd8d8cfa9875cc35baefefba7450c28b0
Tx public key: a3d4819b2a6dcd114384b3512ba3f95d5fa7ce5f63451fd2ee370330ab021d45
Timestamp: 1699042302 Timestamp [UCT]: 2023-11-03 20:11:42 Age [y:d:h:m:s]: 01:156:15:59:24
Block: 884010 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372955 RingCT/type: yes/0
Extra: 01a3d4819b2a6dcd114384b3512ba3f95d5fa7ce5f63451fd2ee370330ab021d4502110000000475e3f0e9000000000000000000

1 output(s) for total of 0.722646555000 dcy

stealth address amount amount idx
00: 1d67d14f121ddf49722e68e1001dd12e3648e1a6df667009cb8ae4e5acd298e7 0.722646555000 1339739 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": 884020, "vin": [ { "gen": { "height": 884010 } } ], "vout": [ { "amount": 722646555, "target": { "key": "1d67d14f121ddf49722e68e1001dd12e3648e1a6df667009cb8ae4e5acd298e7" } } ], "extra": [ 1, 163, 212, 129, 155, 42, 109, 205, 17, 67, 132, 179, 81, 43, 163, 249, 93, 95, 167, 206, 95, 99, 69, 31, 210, 238, 55, 3, 48, 171, 2, 29, 69, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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