Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4efc8d9d69140519ec0c560c16f5115b72f1415cf501c229aef80927671c1260

Tx prefix hash: f41e80f9ff30d7bf9240d36a56da69ffd648337ee8b579740b7d88a9b4ac85f7
Tx public key: 337de7798bbf25f94f20ed9e8af0cb92ec5a3add4e5d18e0610bdf1a712d0709
Timestamp: 1722057614 Timestamp [UCT]: 2024-07-27 05:20:14 Age [y:d:h:m:s]: 00:265:05:07:08
Block: 1074606 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189479 RingCT/type: yes/0
Extra: 01337de7798bbf25f94f20ed9e8af0cb92ec5a3add4e5d18e0610bdf1a712d070902110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3aaf6ff2ac15d0d11db58e7f4321391f100ca8cc568062c065cd4628ee70888d 0.600000000000 1547121 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": 1074616, "vin": [ { "gen": { "height": 1074606 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3aaf6ff2ac15d0d11db58e7f4321391f100ca8cc568062c065cd4628ee70888d" } } ], "extra": [ 1, 51, 125, 231, 121, 139, 191, 37, 249, 79, 32, 237, 158, 138, 240, 203, 146, 236, 90, 58, 221, 78, 93, 24, 224, 97, 11, 223, 26, 113, 45, 7, 9, 2, 17, 0, 0, 0, 8, 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