Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb250bfd29f9e893e6192bf96785ccc8ea449276a3022de5997f663e9f401ec0

Tx prefix hash: cfeb2be92d2d94fb3abeaf66ff41362c7080cb8f9b2b2315636315ec066ebf53
Tx public key: 1f7cbf32852533c7500d9b59604de043e508408b7d0562bb8ae2099cbf359feb
Timestamp: 1724631801 Timestamp [UCT]: 2024-08-26 00:23:21 Age [y:d:h:m:s]: 00:220:21:21:27
Block: 1095947 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157727 RingCT/type: yes/0
Extra: 011f7cbf32852533c7500d9b59604de043e508408b7d0562bb8ae2099cbf359feb02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d7a594c835127aab57ea1c42190a290a1f34e26924ad33d80f5becf4f4cb0dbc 0.600000000000 1571132 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": 1095957, "vin": [ { "gen": { "height": 1095947 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d7a594c835127aab57ea1c42190a290a1f34e26924ad33d80f5becf4f4cb0dbc" } } ], "extra": [ 1, 31, 124, 191, 50, 133, 37, 51, 199, 80, 13, 155, 89, 96, 77, 224, 67, 229, 8, 64, 139, 125, 5, 98, 187, 138, 226, 9, 156, 191, 53, 159, 235, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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