Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36d0a60da8258798fe06a4dacec9f7c9ab43b470d65320529693eb847629b8b1

Tx prefix hash: 8046caf47574b6dd95fa9b017ea221af269d350898dfaf92931896e75589bbc7
Tx public key: 88f70f90b9a450167f3195cb77b3b46fe352d28f117dc5f13eba4a22960a6737
Timestamp: 1752963694 Timestamp [UCT]: 2025-07-19 22:21:34 Age [y:d:h:m:s]: 00:124:20:27:22
Block: 1329117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88023 RingCT/type: yes/0
Extra: 0188f70f90b9a450167f3195cb77b3b46fe352d28f117dc5f13eba4a22960a6737021100000004e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 620b3d39a8188b8e29243d28d4acfd6722a5d1b8fb1fcb4e256fcf1ecfa5dde4 0.600000000000 1816892 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": 1329127, "vin": [ { "gen": { "height": 1329117 } } ], "vout": [ { "amount": 600000000, "target": { "key": "620b3d39a8188b8e29243d28d4acfd6722a5d1b8fb1fcb4e256fcf1ecfa5dde4" } } ], "extra": [ 1, 136, 247, 15, 144, 185, 164, 80, 22, 127, 49, 149, 203, 119, 179, 180, 111, 227, 82, 210, 143, 17, 125, 197, 241, 62, 186, 74, 34, 150, 10, 103, 55, 2, 17, 0, 0, 0, 4, 228, 220, 144, 9, 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