Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3df67306ba8825f99ebf837dabfe4c12bdb881b05e81024288739dd0833ac525

Tx prefix hash: 8406e04a467e052daed9f8f2527867d79cb01feb2b3c4578c69c1ef7c80c0989
Tx public key: 92ae6a9f98cba3f38687d141f8fbc7f8839a406c2cfef77d8500f2e366bb01a2
Timestamp: 1705565318 Timestamp [UCT]: 2024-01-18 08:08:38 Age [y:d:h:m:s]: 01:083:14:59:46
Block: 937864 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320867 RingCT/type: yes/0
Extra: 0192ae6a9f98cba3f38687d141f8fbc7f8839a406c2cfef77d8500f2e366bb01a202110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36d267cfd22b28f4c1383a94e2023ae7faec8398a67e0a9d7fca6385f4f0b624 0.600000000000 1395928 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": 937874, "vin": [ { "gen": { "height": 937864 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36d267cfd22b28f4c1383a94e2023ae7faec8398a67e0a9d7fca6385f4f0b624" } } ], "extra": [ 1, 146, 174, 106, 159, 152, 203, 163, 243, 134, 135, 209, 65, 248, 251, 199, 248, 131, 154, 64, 108, 44, 254, 247, 125, 133, 0, 242, 227, 102, 187, 1, 162, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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