Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d17f6669c7babd33d94f2df8ad4e2f0eb4d2994ce1a8fad2f17ece458809eca

Tx prefix hash: f252f6be879b7dd4664c6ee86ea5dc46844e8756d0172626381910e78a238134
Tx public key: 9113f29d6b45bb7761328673909e80e7d25eb2fc78cec92f5c90cc8f90bf2365
Timestamp: 1712795383 Timestamp [UCT]: 2024-04-11 00:29:43 Age [y:d:h:m:s]: 01:070:16:38:57
Block: 997801 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311386 RingCT/type: yes/0
Extra: 019113f29d6b45bb7761328673909e80e7d25eb2fc78cec92f5c90cc8f90bf23650211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 038e15e8b82f057a4a173c80dcf6793f44a7a1041ecea50c116f94d3cb0e4c83 0.600000000000 1458235 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": 997811, "vin": [ { "gen": { "height": 997801 } } ], "vout": [ { "amount": 600000000, "target": { "key": "038e15e8b82f057a4a173c80dcf6793f44a7a1041ecea50c116f94d3cb0e4c83" } } ], "extra": [ 1, 145, 19, 242, 157, 107, 69, 187, 119, 97, 50, 134, 115, 144, 158, 128, 231, 210, 94, 178, 252, 120, 206, 201, 47, 92, 144, 204, 143, 144, 191, 35, 101, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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