Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c692c8671f2f1f3e51c5241692272bd03fe036fb81dca41f9d7c45cf1f76fed1

Tx prefix hash: be6cdd74f6bb86b59bd482fe5d792393512fb6d23c20c63cb382dde0145c2f92
Tx public key: dd61a932adf0cbe63cfd7e3d24d84037fda8b1bfd7ee10359de102b59d748b74
Timestamp: 1752004267 Timestamp [UCT]: 2025-07-08 19:51:07 Age [y:d:h:m:s]: 00:185:22:34:43
Block: 1321513 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 131436 RingCT/type: yes/0
Extra: 01dd61a932adf0cbe63cfd7e3d24d84037fda8b1bfd7ee10359de102b59d748b740211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6bbdbc5dd55e6b1789064279af01a2fa9f520b8f597516b733a76ab261090704 0.600000000000 1809220 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": 1321523, "vin": [ { "gen": { "height": 1321513 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6bbdbc5dd55e6b1789064279af01a2fa9f520b8f597516b733a76ab261090704" } } ], "extra": [ 1, 221, 97, 169, 50, 173, 240, 203, 230, 60, 253, 126, 61, 36, 216, 64, 55, 253, 168, 177, 191, 215, 238, 16, 53, 157, 225, 2, 181, 157, 116, 139, 116, 2, 17, 0, 0, 0, 1, 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