Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0e9468de7a8d772d15422c3a3ba58d45370e048b0e2d902e8e3d7ef27833946

Tx prefix hash: 1d3537af7eeb7acf2f16b3e6c76feca50d2af2267c16b3403fc1979f9ed3efde
Tx public key: bf9a0c13a883eda1f3e43448f5364972aca72c01e6a55954ebd55dc12bdc4eaf
Timestamp: 1710570778 Timestamp [UCT]: 2024-03-16 06:32:58 Age [y:d:h:m:s]: 00:313:23:22:36
Block: 979408 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224678 RingCT/type: yes/0
Extra: 01bf9a0c13a883eda1f3e43448f5364972aca72c01e6a55954ebd55dc12bdc4eaf0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 04afd0fb7e7d25d832e8eeed5a5b297b9be49a8cd67acf284af56148110b3bca 0.600000000000 1439441 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": 979418, "vin": [ { "gen": { "height": 979408 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04afd0fb7e7d25d832e8eeed5a5b297b9be49a8cd67acf284af56148110b3bca" } } ], "extra": [ 1, 191, 154, 12, 19, 168, 131, 237, 161, 243, 228, 52, 72, 245, 54, 73, 114, 172, 167, 44, 1, 230, 165, 89, 84, 235, 213, 93, 193, 43, 220, 78, 175, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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