Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e5ca51894c48da22a8fd892b744ee8535a3fc69fed07bc0bf1fee263f961c46

Tx prefix hash: 71751c1132b702cfb43e5b26cd8b444353cd70df389ab4b70722437129f5b82c
Tx public key: 021fff797c5acd162fc4545d2d7df71a6bd676feaa9117e4e0b855a153ec0859
Timestamp: 1736866539 Timestamp [UCT]: 2025-01-14 14:55:39 Age [y:d:h:m:s]: 00:155:17:32:43
Block: 1197243 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110993 RingCT/type: yes/0
Extra: 01021fff797c5acd162fc4545d2d7df71a6bd676feaa9117e4e0b855a153ec085902110000000c1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f2b047862e03e0a6c93daad6f934086ac148ded71b4edc7582992e69a8b7458 0.600000000000 1683850 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": 1197253, "vin": [ { "gen": { "height": 1197243 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f2b047862e03e0a6c93daad6f934086ac148ded71b4edc7582992e69a8b7458" } } ], "extra": [ 1, 2, 31, 255, 121, 124, 90, 205, 22, 47, 196, 84, 93, 45, 125, 247, 26, 107, 214, 118, 254, 170, 145, 23, 228, 224, 184, 85, 161, 83, 236, 8, 89, 2, 17, 0, 0, 0, 12, 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