Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1faa70632814dabea30ea15859759ff2398df7c5061eff83a6451904a8c5f54a

Tx prefix hash: f043403572d699e0b9b79df20a8190b021d624ac62fb0d8d602b01c2a5ea0e94
Tx public key: 4a47fbfa4aa6b73eccc17a6d8d6c58bb1f0f8e1182b129b324d9347f70d0e449
Timestamp: 1735296626 Timestamp [UCT]: 2024-12-27 10:50:26 Age [y:d:h:m:s]: 00:084:14:32:08
Block: 1184245 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60251 RingCT/type: yes/0
Extra: 014a47fbfa4aa6b73eccc17a6d8d6c58bb1f0f8e1182b129b324d9347f70d0e449021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf3901495200c140db66461d42b7eb5bf1f91e4f6487f4353f6d554c9e76c4a3 0.600000000000 1670700 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": 1184255, "vin": [ { "gen": { "height": 1184245 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf3901495200c140db66461d42b7eb5bf1f91e4f6487f4353f6d554c9e76c4a3" } } ], "extra": [ 1, 74, 71, 251, 250, 74, 166, 183, 62, 204, 193, 122, 109, 141, 108, 88, 187, 31, 15, 142, 17, 130, 177, 41, 179, 36, 217, 52, 127, 112, 208, 228, 73, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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