Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e33af9b453191d1c64979c0c81dec873c97e5d403b972e6156f3d89d54868780

Tx prefix hash: 5b94bd41a18b7f64caf2882c085814517a9a0bd10a0495b447ccf428cb68f9b9
Tx public key: 047939aee29851c7177ed02bdd152de9fa3d4b90fb514e1b9c593b745ea08e3c
Timestamp: 1693914442 Timestamp [UCT]: 2023-09-05 11:47:22 Age [y:d:h:m:s]: 01:252:18:24:26
Block: 841476 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 441793 RingCT/type: yes/0
Extra: 01047939aee29851c7177ed02bdd152de9fa3d4b90fb514e1b9c593b745ea08e3c02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.999633422000 dcy

stealth address amount amount idx
00: 0508475dcb5749e1f8cfd464ec2ca1704b08645b6d0de9e3a2e408bf48f756a8 0.999633422000 1294512 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": 841486, "vin": [ { "gen": { "height": 841476 } } ], "vout": [ { "amount": 999633422, "target": { "key": "0508475dcb5749e1f8cfd464ec2ca1704b08645b6d0de9e3a2e408bf48f756a8" } } ], "extra": [ 1, 4, 121, 57, 174, 226, 152, 81, 199, 23, 126, 208, 43, 221, 21, 45, 233, 250, 61, 75, 144, 251, 81, 78, 27, 156, 89, 59, 116, 94, 160, 142, 60, 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