Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42f592b46acae4c0107fa893e55ec26222378d541f9c2d52d5b5a61124ee1c1e

Tx prefix hash: f1d55d1126e41d3899f71166d0bc19585de2d4770acbf48d013c01a583e37199
Tx public key: 1812b7efe9e2b67c8dc80ee33e87a9a0133ec660daf22c307635170e154f84e6
Timestamp: 1710200877 Timestamp [UCT]: 2024-03-11 23:47:57 Age [y:d:h:m:s]: 01:024:19:28:42
Block: 976329 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278707 RingCT/type: yes/0
Extra: 011812b7efe9e2b67c8dc80ee33e87a9a0133ec660daf22c307635170e154f84e60211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f19594bc187350d0d891d104dbf6fca753a39c81f41307c4812bc8032e5b121 0.600000000000 1436322 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": 976339, "vin": [ { "gen": { "height": 976329 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f19594bc187350d0d891d104dbf6fca753a39c81f41307c4812bc8032e5b121" } } ], "extra": [ 1, 24, 18, 183, 239, 233, 226, 182, 124, 141, 200, 14, 227, 62, 135, 169, 160, 19, 62, 198, 96, 218, 242, 44, 48, 118, 53, 23, 14, 21, 79, 132, 230, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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