Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a3c11636936a8403eee8c3e198f426f3558d99dff1cd1c571d74fe8c559cb99

Tx prefix hash: 97cb7696e0e3cb894094d2c87bf06f3bc59751f78bbf7cbac4c485c719db7a95
Tx public key: 95a5067004a2f633dc69ff13d6ac2ae445afe071b821306bfe8eb45cc20920da
Timestamp: 1711474035 Timestamp [UCT]: 2024-03-26 17:27:15 Age [y:d:h:m:s]: 00:231:15:17:13
Block: 986898 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165793 RingCT/type: yes/0
Extra: 0195a5067004a2f633dc69ff13d6ac2ae445afe071b821306bfe8eb45cc20920da02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 60e03e3aaef825d9d141bb356a7678c9a7169ad93f86574acf3dc788a5e608c6 0.600000000000 1447135 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": 986908, "vin": [ { "gen": { "height": 986898 } } ], "vout": [ { "amount": 600000000, "target": { "key": "60e03e3aaef825d9d141bb356a7678c9a7169ad93f86574acf3dc788a5e608c6" } } ], "extra": [ 1, 149, 165, 6, 112, 4, 162, 246, 51, 220, 105, 255, 19, 214, 172, 42, 228, 69, 175, 224, 113, 184, 33, 48, 107, 254, 142, 180, 92, 194, 9, 32, 218, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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