Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ea01625f9f6b97909797253d3ab7b7c00792d395d13487256a6838745334fec

Tx prefix hash: f7825e2c47afd6d63ddf49e83a8f610229ff259342d6c2e8333c5fc3d780760c
Tx public key: bce22100a1cd01f653a53e3d4a264e9a0ff260f90770b8a4e94996d3f30b3629
Timestamp: 1740956810 Timestamp [UCT]: 2025-03-02 23:06:50 Age [y:d:h:m:s]: 00:010:11:11:14
Block: 1230837 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7502 RingCT/type: yes/0
Extra: 01bce22100a1cd01f653a53e3d4a264e9a0ff260f90770b8a4e94996d3f30b36290211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9ae5e2fb9d9d432bdd19a94324878baee26a815a5a72cc3c5f308a714824467 0.600000000000 1717740 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": 1230847, "vin": [ { "gen": { "height": 1230837 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9ae5e2fb9d9d432bdd19a94324878baee26a815a5a72cc3c5f308a714824467" } } ], "extra": [ 1, 188, 226, 33, 0, 161, 205, 1, 246, 83, 165, 62, 61, 74, 38, 78, 154, 15, 242, 96, 249, 7, 112, 184, 164, 233, 73, 150, 211, 243, 11, 54, 41, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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