Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9c5aff4a865cc04f057eaf26d71fb310f7a20c3501116472514e9903b73f6ad

Tx prefix hash: f4e366fc7b86f80b303c81bfcb3773db7389b67f1fdfbf421e29aedcd0a610a5
Tx public key: 6d876cf9c3a139e812987fb65e3a4571fa1efe09dd20f5c6e9645a9a60427cf0
Timestamp: 1761735560 Timestamp [UCT]: 2025-10-29 10:59:20 Age [y:d:h:m:s]: 00:014:05:56:45
Block: 1400459 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10184 RingCT/type: yes/0
Extra: 016d876cf9c3a139e812987fb65e3a4571fa1efe09dd20f5c6e9645a9a60427cf00211000000038368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68db084d493dab4fd494c40946f1e48e32d3887127cd6dc23187416395e55d2e 0.600000000000 1888768 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": 1400469, "vin": [ { "gen": { "height": 1400459 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68db084d493dab4fd494c40946f1e48e32d3887127cd6dc23187416395e55d2e" } } ], "extra": [ 1, 109, 135, 108, 249, 195, 161, 57, 232, 18, 152, 127, 182, 94, 58, 69, 113, 250, 30, 254, 9, 221, 32, 245, 198, 233, 100, 90, 154, 96, 66, 124, 240, 2, 17, 0, 0, 0, 3, 131, 104, 38, 109, 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