Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58af06b0892445896a41de3f735345b922eaac3ba45d348414e61009044fd63d

Tx prefix hash: 93bb07499cda1750042c9a92497e1112e1a53c76a4bca6fa3b847c50f4167bd3
Tx public key: e81dfae45704ca20c72f3119e45e67f8f5bbcc3b58cd23f2266d012adc4a045c
Timestamp: 1703576787 Timestamp [UCT]: 2023-12-26 07:46:27 Age [y:d:h:m:s]: 01:174:12:07:26
Block: 921394 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 385768 RingCT/type: yes/0
Extra: 01e81dfae45704ca20c72f3119e45e67f8f5bbcc3b58cd23f2266d012adc4a045c02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e75db5a1cf98b852f676b13a6f472255a399ba2b9c385c8768ae816062fc9c1 0.600000000000 1379082 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": 921404, "vin": [ { "gen": { "height": 921394 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e75db5a1cf98b852f676b13a6f472255a399ba2b9c385c8768ae816062fc9c1" } } ], "extra": [ 1, 232, 29, 250, 228, 87, 4, 202, 32, 199, 47, 49, 25, 228, 94, 103, 248, 245, 187, 204, 59, 88, 205, 35, 242, 38, 109, 1, 42, 220, 74, 4, 92, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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