Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a89dd19b1bbda5bce3820b9688493bde96ca8d6719883eba49392ac6d2fd779

Tx prefix hash: d5a418a5b7707ad604d2ef6e91472e7f3eb8d0e292ea7b5f0980c00a97783e2c
Tx public key: 09b27abcdb6aee0e24dfeb2802db709e5bacd43bb73e487d01f0398c007df86b
Timestamp: 1717001700 Timestamp [UCT]: 2024-05-29 16:55:00 Age [y:d:h:m:s]: 00:313:07:47:31
Block: 1032696 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 223920 RingCT/type: yes/0
Extra: 0109b27abcdb6aee0e24dfeb2802db709e5bacd43bb73e487d01f0398c007df86b0211000000090011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0f274de60f3c7d58cfb78b18b12591e0366f81a6ae99d94d0d1bec89d7ce353 0.600000000000 1501149 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": 1032706, "vin": [ { "gen": { "height": 1032696 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0f274de60f3c7d58cfb78b18b12591e0366f81a6ae99d94d0d1bec89d7ce353" } } ], "extra": [ 1, 9, 178, 122, 188, 219, 106, 238, 14, 36, 223, 235, 40, 2, 219, 112, 158, 91, 172, 212, 59, 183, 62, 72, 125, 1, 240, 57, 140, 0, 125, 248, 107, 2, 17, 0, 0, 0, 9, 0, 17, 5, 91, 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