Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 696c843ac78e5936bf405e8f9e3d45b8ae6088d7730e8dab078905fac376779c

Tx prefix hash: fe9cfe3a122019368af5d6d4428fd1f74ebda08cbf2284d15c24bfa9d511789a
Tx public key: 6c23b7d7a0c32a35b4b272e05857fa2201e4cc8c857070ad852153bba12e4f9b
Timestamp: 1766303986 Timestamp [UCT]: 2025-12-21 07:59:46 Age [y:d:h:m:s]: 00:001:00:33:20
Block: 1438310 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 719 RingCT/type: yes/0
Extra: 016c23b7d7a0c32a35b4b272e05857fa2201e4cc8c857070ad852153bba12e4f9b02110000000ed6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2fd215f84358ab5cf2052b3ef3450511a010beeb484669c082194136f8eb6359 0.600000000000 1927127 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": 1438320, "vin": [ { "gen": { "height": 1438310 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2fd215f84358ab5cf2052b3ef3450511a010beeb484669c082194136f8eb6359" } } ], "extra": [ 1, 108, 35, 183, 215, 160, 195, 42, 53, 180, 178, 114, 224, 88, 87, 250, 34, 1, 228, 204, 140, 133, 112, 112, 173, 133, 33, 83, 187, 161, 46, 79, 155, 2, 17, 0, 0, 0, 14, 214, 225, 157, 124, 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