Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f83bf6b318c5b4cbe9233a650937016ec68b9da56837a601948ab78c3f9aa7f7

Tx prefix hash: dd5237c04edb9f7e2332f087beebbc1667c712742386763af9b08f6d3802dce6
Tx public key: 2ef7cb3f7c05dcafc1674f593e262072b73de9f47bd48473d30c16e535bdd67d
Timestamp: 1757017454 Timestamp [UCT]: 2025-09-04 20:24:14 Age [y:d:h:m:s]: 00:109:10:34:02
Block: 1361410 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78285 RingCT/type: yes/0
Extra: 012ef7cb3f7c05dcafc1674f593e262072b73de9f47bd48473d30c16e535bdd67d021100000005b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f3580e979f36007663a26690304753072c3196b87a6b4df0259e6548f889923e 0.600000000000 1849425 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": 1361420, "vin": [ { "gen": { "height": 1361410 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3580e979f36007663a26690304753072c3196b87a6b4df0259e6548f889923e" } } ], "extra": [ 1, 46, 247, 203, 63, 124, 5, 220, 175, 193, 103, 79, 89, 62, 38, 32, 114, 183, 61, 233, 244, 123, 212, 132, 115, 211, 12, 22, 229, 53, 189, 214, 125, 2, 17, 0, 0, 0, 5, 178, 247, 132, 196, 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