Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04f8a802748c13c4c97a405baab4128fc133274670e601711f3011d3d9baa4e3

Tx prefix hash: 75ace87e084bad8b7581d91d71ea9e6a8d6cbd85e261c13511d763727f744a25
Tx public key: 4d96dccf4a43f1b3cc934c1afbc576add44f2d19455ee05a92012cca6bdb73a8
Timestamp: 1755765840 Timestamp [UCT]: 2025-08-21 08:44:00 Age [y:d:h:m:s]: 00:090:23:10:49
Block: 1351174 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64926 RingCT/type: yes/0
Extra: 014d96dccf4a43f1b3cc934c1afbc576add44f2d19455ee05a92012cca6bdb73a8021100000007b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3caa2f98452906927034369d27d6067b87814e2252e90212285ff7d371e1eda6 0.600000000000 1839123 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": 1351184, "vin": [ { "gen": { "height": 1351174 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3caa2f98452906927034369d27d6067b87814e2252e90212285ff7d371e1eda6" } } ], "extra": [ 1, 77, 150, 220, 207, 74, 67, 241, 179, 204, 147, 76, 26, 251, 197, 118, 173, 212, 79, 45, 25, 69, 94, 224, 90, 146, 1, 44, 202, 107, 219, 115, 168, 2, 17, 0, 0, 0, 7, 178, 247, 132, 196, 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