Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7d9a16ca62a8b5f578c78c93974f014e7fe404dd5b29e05c74136a1492a05d3

Tx prefix hash: eca43b7a8caba4ce2a8e5e1cee44e3fba3b1802e596880da407d11fa0bcd94a0
Tx public key: aec708ed5fd43bf78577df62c12004d79183a67f99cf97f8489383b2ecbb0858
Timestamp: 1696953082 Timestamp [UCT]: 2023-10-10 15:51:22 Age [y:d:h:m:s]: 01:141:20:26:46
Block: 866698 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362374 RingCT/type: yes/0
Extra: 01aec708ed5fd43bf78577df62c12004d79183a67f99cf97f8489383b2ecbb085802110000000ee6d27f9c000000000000000000

1 output(s) for total of 0.824650212000 dcy

stealth address amount amount idx
00: 8beb1679761bb859fb469365500023c95184dd3aa284e9ac3d63f40e0031ebcf 0.824650212000 1321322 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": 866708, "vin": [ { "gen": { "height": 866698 } } ], "vout": [ { "amount": 824650212, "target": { "key": "8beb1679761bb859fb469365500023c95184dd3aa284e9ac3d63f40e0031ebcf" } } ], "extra": [ 1, 174, 199, 8, 237, 95, 212, 59, 247, 133, 119, 223, 98, 193, 32, 4, 215, 145, 131, 166, 127, 153, 207, 151, 248, 72, 147, 131, 178, 236, 187, 8, 88, 2, 17, 0, 0, 0, 14, 230, 210, 127, 156, 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