Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a0657b1cfb67a9a674506092519b2cfef52884ccc291043c9019cae1d5c67c5

Tx prefix hash: ea9be85fe89267dffafcc40815929f4b30956eadad6f4cf238b7b644e42d9acd
Tx public key: e106d7f237061220b5f7f80a8e2183fcaf38ad427ab69a590b8ac596b16dcf03
Timestamp: 1707261712 Timestamp [UCT]: 2024-02-06 23:21:52 Age [y:d:h:m:s]: 00:267:14:11:51
Block: 951937 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191618 RingCT/type: yes/0
Extra: 01e106d7f237061220b5f7f80a8e2183fcaf38ad427ab69a590b8ac596b16dcf0302110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4a6e9f5acb9625e5b9d547763cb706add78bdc001739968f8b18b62ac1f5b90 0.600000000000 1410785 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": 951947, "vin": [ { "gen": { "height": 951937 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4a6e9f5acb9625e5b9d547763cb706add78bdc001739968f8b18b62ac1f5b90" } } ], "extra": [ 1, 225, 6, 215, 242, 55, 6, 18, 32, 181, 247, 248, 10, 142, 33, 131, 252, 175, 56, 173, 66, 122, 182, 154, 89, 11, 138, 197, 150, 177, 109, 207, 3, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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