Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c7cd1dadf79b5da313ff1e0be6a652ff26bfa8d8e4bd5387a60a9e0624f07ff

Tx prefix hash: b98ac5549b8ec44c0ce37a300ec5fc090ff9dc21d6b65aee8756f17340649b04
Tx public key: 321d327a5bc2c628d621fd7e48f3014c600f878b62b900c7cddc6e2da79cdbf4
Timestamp: 1760146268 Timestamp [UCT]: 2025-10-11 01:31:08 Age [y:d:h:m:s]: 00:078:18:18:41
Block: 1387267 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 56403 RingCT/type: yes/0
Extra: 01321d327a5bc2c628d621fd7e48f3014c600f878b62b900c7cddc6e2da79cdbf4021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7d20d8738b7873be4790caded234186f50a74cdd2ec9928948d314ed50387a2 0.600000000000 1875454 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": 1387277, "vin": [ { "gen": { "height": 1387267 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7d20d8738b7873be4790caded234186f50a74cdd2ec9928948d314ed50387a2" } } ], "extra": [ 1, 50, 29, 50, 122, 91, 194, 198, 40, 214, 33, 253, 126, 72, 243, 1, 76, 96, 15, 135, 139, 98, 185, 0, 199, 205, 220, 110, 45, 167, 156, 219, 244, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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