Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f6c1784033827179d8577efd382dd29d757745d3fc03c6526b475d17932a9b6

Tx prefix hash: a70fb715c5ce1f2e1ff2b40458d34e76077a63c79ccdc8b13d2b1ab1a288e1c8
Tx public key: e9cf77c0e489024cab7e30c00058151feef3a5371475f9037b2ba8091f75a0b1
Timestamp: 1674714856 Timestamp [UCT]: 2023-01-26 06:34:16 Age [y:d:h:m:s]: 01:355:18:17:56
Block: 682997 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 515249 RingCT/type: yes/0
Extra: 01e9cf77c0e489024cab7e30c00058151feef3a5371475f9037b2ba8091f75a0b10211000000025029cbac000000000000000000

1 output(s) for total of 3.349248347000 dcy

stealth address amount amount idx
00: b75cb10335e13945e9d56f25dd5770d3ae373cb9a93ebad0eb6113b312d91092 3.349248347000 1125142 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": 683007, "vin": [ { "gen": { "height": 682997 } } ], "vout": [ { "amount": 3349248347, "target": { "key": "b75cb10335e13945e9d56f25dd5770d3ae373cb9a93ebad0eb6113b312d91092" } } ], "extra": [ 1, 233, 207, 119, 192, 228, 137, 2, 76, 171, 126, 48, 192, 0, 88, 21, 31, 238, 243, 165, 55, 20, 117, 249, 3, 123, 43, 168, 9, 31, 117, 160, 177, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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