Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 832cc755f6f821a6c2f0489e162c89e595c9809e1a8bfa3bf0afd6d4e10bb6d6

Tx prefix hash: 59eaafd90e409e12c1ac75fe16cb60fb8d098b10509f30d91696341535c93edb
Tx public key: 21305df65602a69093ac50ab8b426e8df834aa67fe027534bae8b6a00d016593
Timestamp: 1763087166 Timestamp [UCT]: 2025-11-14 02:26:06 Age [y:d:h:m:s]: 00:050:10:25:20
Block: 1411648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 36110 RingCT/type: yes/0
Extra: 0121305df65602a69093ac50ab8b426e8df834aa67fe027534bae8b6a00d0165930211000000052609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 59834f5cddb8e5b8f2f21b301c76d6a657952ec7c753e2a3dec19675069dc8f8 0.600000000000 1900111 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": 1411658, "vin": [ { "gen": { "height": 1411648 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59834f5cddb8e5b8f2f21b301c76d6a657952ec7c753e2a3dec19675069dc8f8" } } ], "extra": [ 1, 33, 48, 93, 246, 86, 2, 166, 144, 147, 172, 80, 171, 139, 66, 110, 141, 248, 52, 170, 103, 254, 2, 117, 52, 186, 232, 182, 160, 13, 1, 101, 147, 2, 17, 0, 0, 0, 5, 38, 9, 179, 160, 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