Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ebf9e9bffb8c67791c4d2ca85038f95b5d8a576c523f805d4efe7d85c6b7446

Tx prefix hash: 5df64f74ec6c6da1e825e0daf08266279e6f1d5971ae1c74ab19aff84b35cac5
Tx public key: 1cfcb34aa84468c9670b25425a38838871b5e13c9a6722841c2ce4d9356773f3
Timestamp: 1744929015 Timestamp [UCT]: 2025-04-17 22:30:15 Age [y:d:h:m:s]: 00:207:02:44:38
Block: 1263707 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145746 RingCT/type: yes/0
Extra: 011cfcb34aa84468c9670b25425a38838871b5e13c9a6722841c2ce4d9356773f3021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5ba0ee278759e8a9af2eafd171194639d9fb0dc73c7d0321f92932a891e9be2 0.600000000000 1750900 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": 1263717, "vin": [ { "gen": { "height": 1263707 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5ba0ee278759e8a9af2eafd171194639d9fb0dc73c7d0321f92932a891e9be2" } } ], "extra": [ 1, 28, 252, 179, 74, 168, 68, 104, 201, 103, 11, 37, 66, 90, 56, 131, 136, 113, 181, 225, 60, 154, 103, 34, 132, 28, 44, 228, 217, 53, 103, 115, 243, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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