Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4be09ccb5e88307939f89be0b7e6bbf15ca6d41f23283f602dfbdd151526fa4f

Tx prefix hash: c44354b87dba4b9993627d2dd5e1a8b71c5afa74f27fbb9abc4a814d771382e6
Tx public key: 3f8f5e6f82257a3c3c25f95ff31254297e73f64778ff5615ec87de6ca7e29901
Timestamp: 1751069983 Timestamp [UCT]: 2025-06-28 00:19:43 Age [y:d:h:m:s]: 00:145:21:32:29
Block: 1314150 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102365 RingCT/type: yes/0
Extra: 013f8f5e6f82257a3c3c25f95ff31254297e73f64778ff5615ec87de6ca7e29901021100000002bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2aeabbf271367340bda11d0827287aa126054fcdc6295b95391978a79e5db6fb 0.600000000000 1801795 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": 1314160, "vin": [ { "gen": { "height": 1314150 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2aeabbf271367340bda11d0827287aa126054fcdc6295b95391978a79e5db6fb" } } ], "extra": [ 1, 63, 143, 94, 111, 130, 37, 122, 60, 60, 37, 249, 95, 243, 18, 84, 41, 126, 115, 246, 71, 120, 255, 86, 21, 236, 135, 222, 108, 167, 226, 153, 1, 2, 17, 0, 0, 0, 2, 191, 81, 178, 162, 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