Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29acb86909eb44e0b9c46c11926d550ee3921c6bd6afe4309569443e0131ceb2

Tx prefix hash: 0b26afcc7c7d4d5b7545dee6556f282711feb0056b25e5d1c018bac8aeca7e99
Tx public key: 111f18fbb93c29d3a8fcb89268b37c68e356af5177a4acb493a0a961f0e73347
Timestamp: 1577798928 Timestamp [UCT]: 2019-12-31 13:28:48 Age [y:d:h:m:s]: 04:334:23:04:52
Block: 35786 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1128490 RingCT/type: yes/0
Extra: 01111f18fbb93c29d3a8fcb89268b37c68e356af5177a4acb493a0a961f0e733470211000000114ac5aa02000000000000000000

1 output(s) for total of 467.118406084000 dcy

stealth address amount amount idx
00: 771cbae5fd43d4a146556327c85cd6e14068ef5571e9062228025be3934e7d1c 467.118406084000 60416 of 0

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": 35796, "vin": [ { "gen": { "height": 35786 } } ], "vout": [ { "amount": 467118406084, "target": { "key": "771cbae5fd43d4a146556327c85cd6e14068ef5571e9062228025be3934e7d1c" } } ], "extra": [ 1, 17, 31, 24, 251, 185, 60, 41, 211, 168, 252, 184, 146, 104, 179, 124, 104, 227, 86, 175, 81, 119, 164, 172, 180, 147, 160, 169, 97, 240, 231, 51, 71, 2, 17, 0, 0, 0, 17, 74, 197, 170, 2, 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