Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91163d201af9ea46b8b4fa754a64f50904c6b36b84597848c275c5f684d97839

Tx prefix hash: 056d63c814230bb3880f07d0257b039a9cdc0f2018f01ca4d1738494c41ac786
Tx public key: ace8a1e35ff05e3e8120a2afdf8f1a1663e212ba57b6bce842868797c56e0790
Timestamp: 1750543982 Timestamp [UCT]: 2025-06-21 22:13:02 Age [y:d:h:m:s]: 00:152:06:15:02
Block: 1310044 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106656 RingCT/type: yes/0
Extra: 01ace8a1e35ff05e3e8120a2afdf8f1a1663e212ba57b6bce842868797c56e07900211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2a1b1ebdb204ff3a8bf13a3f869f32dc392e2690d7bab482325db204d6a8b85 0.600000000000 1797661 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": 1310054, "vin": [ { "gen": { "height": 1310044 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2a1b1ebdb204ff3a8bf13a3f869f32dc392e2690d7bab482325db204d6a8b85" } } ], "extra": [ 1, 172, 232, 161, 227, 95, 240, 94, 62, 129, 32, 162, 175, 223, 143, 26, 22, 99, 226, 18, 186, 87, 182, 188, 232, 66, 134, 135, 151, 197, 110, 7, 144, 2, 17, 0, 0, 0, 2, 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