Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e244685ed375ef183405a99e0dd9b3ac5515d3cac738ababb045e029ec6d95c

Tx prefix hash: 011a5d65fd94b08490fdf74d716106cfc73e000f477a9dc3c6194000c47fdc2f
Tx public key: 95efdd8d270cb9f7a0b9a4e974b09cc88044fe1c556ab1b963eeb39fd29d077c
Timestamp: 1672142512 Timestamp [UCT]: 2022-12-27 12:01:52 Age [y:d:h:m:s]: 02:109:08:16:56
Block: 661668 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 599848 RingCT/type: yes/0
Extra: 0195efdd8d270cb9f7a0b9a4e974b09cc88044fe1c556ab1b963eeb39fd29d077c021100000001e7ace25d000000000000000000

1 output(s) for total of 3.941115966000 dcy

stealth address amount amount idx
00: d1ea79b0dcbfdfe629a0878ff1d21cfbce6d945943e6ce65bb2abdcebc6d4281 3.941115966000 1102457 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": 661678, "vin": [ { "gen": { "height": 661668 } } ], "vout": [ { "amount": 3941115966, "target": { "key": "d1ea79b0dcbfdfe629a0878ff1d21cfbce6d945943e6ce65bb2abdcebc6d4281" } } ], "extra": [ 1, 149, 239, 221, 141, 39, 12, 185, 247, 160, 185, 164, 233, 116, 176, 156, 200, 128, 68, 254, 28, 85, 106, 177, 185, 99, 238, 179, 159, 210, 157, 7, 124, 2, 17, 0, 0, 0, 1, 231, 172, 226, 93, 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