Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 364dca0cc8902b526c8db25ae6ad930873dc4a9112788d5191b620b7495fe7fd

Tx prefix hash: 5269e1da72d24254cd0f969c85125f8940ec4fc8228c5d2ad3fbcfc90d66f666
Tx public key: 94815198692731ab20988f06d7fc3a2e50c101e533cee37422aee690f782bd6a
Timestamp: 1715762395 Timestamp [UCT]: 2024-05-15 08:39:55 Age [y:d:h:m:s]: 00:330:14:09:58
Block: 1022430 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236292 RingCT/type: yes/0
Extra: 0194815198692731ab20988f06d7fc3a2e50c101e533cee37422aee690f782bd6a021100000001e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8526480e8b296f482e8a13341c4d229cd364f19e0ed3ff0f9b6cb2b02818fb0e 0.600000000000 1487031 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": 1022440, "vin": [ { "gen": { "height": 1022430 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8526480e8b296f482e8a13341c4d229cd364f19e0ed3ff0f9b6cb2b02818fb0e" } } ], "extra": [ 1, 148, 129, 81, 152, 105, 39, 49, 171, 32, 152, 143, 6, 215, 252, 58, 46, 80, 193, 1, 229, 51, 206, 227, 116, 34, 174, 230, 144, 247, 130, 189, 106, 2, 17, 0, 0, 0, 1, 224, 133, 50, 182, 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