Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec87451fec229a443ce9d76b6591c276b4fa450dd3651f6a5181eb9f1c56aff2

Tx prefix hash: e21ef37b211f6bd28f44eded2fc0c9c72925d26c219fa475db0e9fab91ce6013
Tx public key: f283e3f2781dd7ff74bd6be8403aca79cee5abe1a7e95884b8fbd4b4bf80e478
Timestamp: 1614721515 Timestamp [UCT]: 2021-03-02 21:45:15 Age [y:d:h:m:s]: 03:271:14:33:06
Block: 210133 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 953416 RingCT/type: yes/0
Extra: 01f283e3f2781dd7ff74bd6be8403aca79cee5abe1a7e95884b8fbd4b4bf80e4780211000000213634f08d000000000000000000

1 output(s) for total of 123.521554707000 dcy

stealth address amount amount idx
00: 1b4583f348375d67f8620f05e02f0c4eecba02b58038d82c53f5d15391b8e613 123.521554707000 428568 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": 210143, "vin": [ { "gen": { "height": 210133 } } ], "vout": [ { "amount": 123521554707, "target": { "key": "1b4583f348375d67f8620f05e02f0c4eecba02b58038d82c53f5d15391b8e613" } } ], "extra": [ 1, 242, 131, 227, 242, 120, 29, 215, 255, 116, 189, 107, 232, 64, 58, 202, 121, 206, 229, 171, 225, 167, 233, 88, 132, 184, 251, 212, 180, 191, 128, 228, 120, 2, 17, 0, 0, 0, 33, 54, 52, 240, 141, 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