Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0575b28a761d54b3be1504b1894ff1f6f7ecd606e8f7e8792b9f2dafccd6ddd0

Tx prefix hash: 1de446f04d45f5e0542c3ff441e9a49f9bffbdc412b07be683bbbbd9533a5a30
Tx public key: d5e7ec1f466d71f15f3ff5d6f41e734faea810e94ae86c40f5df4d6167e8f10c
Timestamp: 1708530723 Timestamp [UCT]: 2024-02-21 15:52:03 Age [y:d:h:m:s]: 01:047:14:11:53
Block: 962469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295034 RingCT/type: yes/0
Extra: 01d5e7ec1f466d71f15f3ff5d6f41e734faea810e94ae86c40f5df4d6167e8f10c0211000000090011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b69026ee989e163d9dccef981240cfdc0a266822073d9f3b01c70710f7125ba8 0.600000000000 1422106 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": 962479, "vin": [ { "gen": { "height": 962469 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b69026ee989e163d9dccef981240cfdc0a266822073d9f3b01c70710f7125ba8" } } ], "extra": [ 1, 213, 231, 236, 31, 70, 109, 113, 241, 95, 63, 245, 214, 244, 30, 115, 79, 174, 168, 16, 233, 74, 232, 108, 64, 245, 223, 77, 97, 103, 232, 241, 12, 2, 17, 0, 0, 0, 9, 0, 17, 5, 91, 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