Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d39dd88f1c5b829a4096e0d48482e58c3f989165eea430bdd92c0f1f6ceea83d

Tx prefix hash: 784330bf1a7e0328fc49911e7edb4ee2efec41ee365d9e30302d33f766bf1eaf
Tx public key: a76fe8b20e988507b742f1aa50c2ad82761d689af1eaf687609f20d01d6c18f1
Timestamp: 1737434265 Timestamp [UCT]: 2025-01-21 04:37:45 Age [y:d:h:m:s]: 00:057:05:54:48
Block: 1201895 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40748 RingCT/type: yes/0
Extra: 01a76fe8b20e988507b742f1aa50c2ad82761d689af1eaf687609f20d01d6c18f10211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 14d3c203aade72903fdbd7d5cd0c16f127646a258c2b6a0981c93d69a4bbe903 0.600000000000 1688552 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": 1201905, "vin": [ { "gen": { "height": 1201895 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14d3c203aade72903fdbd7d5cd0c16f127646a258c2b6a0981c93d69a4bbe903" } } ], "extra": [ 1, 167, 111, 232, 178, 14, 152, 133, 7, 183, 66, 241, 170, 80, 194, 173, 130, 118, 29, 104, 154, 241, 234, 246, 135, 96, 159, 32, 208, 29, 108, 24, 241, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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