Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9900e08d84dd574f85c6385fa8d458241f3b756707d5e11ab77d85e9d5d41fff

Tx prefix hash: 2d17443866e6992e4bfe49f142c996db87f6ac6fb1fdc74c1ed79527565e1abc
Tx public key: bbe34afa578e50e761e1944cfe9c4dc8ef9f33c833551d92b4631cdd1725cf2a
Timestamp: 1701540026 Timestamp [UCT]: 2023-12-02 18:00:26 Age [y:d:h:m:s]: 01:083:14:12:49
Block: 904511 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320853 RingCT/type: yes/0
Extra: 01bbe34afa578e50e761e1944cfe9c4dc8ef9f33c833551d92b4631cdd1725cf2a021100000002e08532b6000000000000000000

1 output(s) for total of 0.617987305000 dcy

stealth address amount amount idx
00: eef49bb731bef138506066cfdf4e2a239b051dede031c0e9268dad5b824e80f5 0.617987305000 1361270 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": 904521, "vin": [ { "gen": { "height": 904511 } } ], "vout": [ { "amount": 617987305, "target": { "key": "eef49bb731bef138506066cfdf4e2a239b051dede031c0e9268dad5b824e80f5" } } ], "extra": [ 1, 187, 227, 74, 250, 87, 142, 80, 231, 97, 225, 148, 76, 254, 156, 77, 200, 239, 159, 51, 200, 51, 85, 29, 146, 180, 99, 28, 221, 23, 37, 207, 42, 2, 17, 0, 0, 0, 2, 224, 133, 50, 182, 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