Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: abaa656b20dcb1834eff2a1363906d21e3f657470d613618ba06451ef35b7b07

Tx prefix hash: 37f6c36002e871c5aa0a26ab5444de9831e2d473ff3e547842954c42a4cc7aec
Tx public key: 17f7d5a11dcf555d1a06c55cc81ab4a7e322cb34333da77426ec8787e30a8184
Timestamp: 1698313584 Timestamp [UCT]: 2023-10-26 09:46:24 Age [y:d:h:m:s]: 01:164:09:26:26
Block: 877988 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378471 RingCT/type: yes/0
Extra: 0117f7d5a11dcf555d1a06c55cc81ab4a7e322cb34333da77426ec8787e30a81840211000000074b8f5122000000000000000000

1 output(s) for total of 0.756591228000 dcy

stealth address amount amount idx
00: b0c4b2e031a50313f01e3e7a6c303c889d12324149697efce9a38df1b702df07 0.756591228000 1333392 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": 877998, "vin": [ { "gen": { "height": 877988 } } ], "vout": [ { "amount": 756591228, "target": { "key": "b0c4b2e031a50313f01e3e7a6c303c889d12324149697efce9a38df1b702df07" } } ], "extra": [ 1, 23, 247, 213, 161, 29, 207, 85, 93, 26, 6, 197, 92, 200, 26, 180, 167, 227, 34, 203, 52, 51, 61, 167, 116, 38, 236, 135, 135, 227, 10, 129, 132, 2, 17, 0, 0, 0, 7, 75, 143, 81, 34, 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