Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 593a517cd0ecddd584c0f5d4aa382eeb5e70dd344cc278eb8c4fb40bad9d195c

Tx prefix hash: 21f9633cff78ab9472a2577d6854f85b24f6cde095630d1097e56316884d63fe
Tx public key: b761268fa88cd8b8c192a6bbb6bffcf8670230e0a922936e2214ff2da4e24239
Timestamp: 1761833812 Timestamp [UCT]: 2025-10-30 14:16:52 Age [y:d:h:m:s]: 00:011:01:52:08
Block: 1401263 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7934 RingCT/type: yes/0
Extra: 01b761268fa88cd8b8c192a6bbb6bffcf8670230e0a922936e2214ff2da4e2423902110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 875fa0530c1fe091d6c8a8678e4bf550a8901f8b1e2b1e2303a7b751315d4014 0.600000000000 1889582 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": 1401273, "vin": [ { "gen": { "height": 1401263 } } ], "vout": [ { "amount": 600000000, "target": { "key": "875fa0530c1fe091d6c8a8678e4bf550a8901f8b1e2b1e2303a7b751315d4014" } } ], "extra": [ 1, 183, 97, 38, 143, 168, 140, 216, 184, 193, 146, 166, 187, 182, 191, 252, 248, 103, 2, 48, 224, 169, 34, 147, 110, 34, 20, 255, 45, 164, 226, 66, 57, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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