Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 646ededc540746af3e40a6d028c61984262608d94d8a225f1f164da533bd33a4

Tx prefix hash: a38cc045ff08c0104ab1b9d63795f6d9c016199aa12f8e779988e0838a6f6f7d
Tx public key: fef05369f44a3b3c556935fad8f0cfcc5ffdcfcf3189ee2219e1c775b7b85336
Timestamp: 1764531515 Timestamp [UCT]: 2025-11-30 19:38:35 Age [y:d:h:m:s]: 00:036:04:06:45
Block: 1423621 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 25912 RingCT/type: yes/0
Extra: 01fef05369f44a3b3c556935fad8f0cfcc5ffdcfcf3189ee2219e1c775b7b85336021100000004d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 326dd326e76e9929b7c67eebc7543894754ef088e7b6d457103dc2119f28c6fc 0.600000000000 1912238 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": 1423631, "vin": [ { "gen": { "height": 1423621 } } ], "vout": [ { "amount": 600000000, "target": { "key": "326dd326e76e9929b7c67eebc7543894754ef088e7b6d457103dc2119f28c6fc" } } ], "extra": [ 1, 254, 240, 83, 105, 244, 74, 59, 60, 85, 105, 53, 250, 216, 240, 207, 204, 95, 253, 207, 207, 49, 137, 238, 34, 25, 225, 199, 117, 183, 184, 83, 54, 2, 17, 0, 0, 0, 4, 214, 225, 157, 124, 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