Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0eda4f6e07f8b925b3cd874dca08b48c647e49f02a40b2dfc3481869ba381175

Tx prefix hash: edda799787d85c651201a309cd7038d092c4139e8abb0c5ec8180c23e7b14a09
Tx public key: 27f041f4aa2ef6dde48aa9bd2975b8fdee0187c454ac66690d9af706743d0f23
Timestamp: 1703047764 Timestamp [UCT]: 2023-12-20 04:49:24 Age [y:d:h:m:s]: 01:156:19:22:44
Block: 917019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 373231 RingCT/type: yes/0
Extra: 0127f041f4aa2ef6dde48aa9bd2975b8fdee0187c454ac66690d9af706743d0f2302110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db7b4a46b906b44633ad26526cf0c8448775cc629e28d59a2e56a41db4f2bf0d 0.600000000000 1374583 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": 917029, "vin": [ { "gen": { "height": 917019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db7b4a46b906b44633ad26526cf0c8448775cc629e28d59a2e56a41db4f2bf0d" } } ], "extra": [ 1, 39, 240, 65, 244, 170, 46, 246, 221, 228, 138, 169, 189, 41, 117, 184, 253, 238, 1, 135, 196, 84, 172, 102, 105, 13, 154, 247, 6, 116, 61, 15, 35, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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