Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76e9bb034b529d76b7c999b17d75cf9569d6a6aa7360de080d800fffd6e95ec4

Tx prefix hash: c64749029fe4627ada541147f89bb793da2304c01f893690b67e1c817d4a4732
Tx public key: d6cf050c5d1f9c3f009630a7e840cc814582d072b114210e40e93fe81ad49c1d
Timestamp: 1710660917 Timestamp [UCT]: 2024-03-17 07:35:17 Age [y:d:h:m:s]: 01:239:05:21:59
Block: 980153 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 429655 RingCT/type: yes/0
Extra: 01d6cf050c5d1f9c3f009630a7e840cc814582d072b114210e40e93fe81ad49c1d02110000000c7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1402499be6d2f558915b1bed0e32e3586483ad5705c661619793530a15d60218 0.600000000000 1440212 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": 980163, "vin": [ { "gen": { "height": 980153 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1402499be6d2f558915b1bed0e32e3586483ad5705c661619793530a15d60218" } } ], "extra": [ 1, 214, 207, 5, 12, 93, 31, 156, 63, 0, 150, 48, 167, 232, 64, 204, 129, 69, 130, 208, 114, 177, 20, 33, 14, 64, 233, 63, 232, 26, 212, 156, 29, 2, 17, 0, 0, 0, 12, 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