Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83a8adc387fca5e959f0539607ad937cab309e2ed1ea467b3f18ba49dc70161c

Tx prefix hash: 35dbd2f39e58bdf8293ceabe11bbac2d000e94db1b7c9f0a5233fef6e321f5a3
Tx public key: 3775963dd8c902a1b7a50f189dc57e56aa9db413404d3079e6b85fe44af320ce
Timestamp: 1712256142 Timestamp [UCT]: 2024-04-04 18:42:22 Age [y:d:h:m:s]: 01:040:04:28:55
Block: 993338 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289726 RingCT/type: yes/0
Extra: 013775963dd8c902a1b7a50f189dc57e56aa9db413404d3079e6b85fe44af320ce0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 799c80625d69377a767ceb0296abc0c42bba77aa01eadcd7d79e989be50b1f17 0.600000000000 1453724 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": 993348, "vin": [ { "gen": { "height": 993338 } } ], "vout": [ { "amount": 600000000, "target": { "key": "799c80625d69377a767ceb0296abc0c42bba77aa01eadcd7d79e989be50b1f17" } } ], "extra": [ 1, 55, 117, 150, 61, 216, 201, 2, 161, 183, 165, 15, 24, 157, 197, 126, 86, 170, 157, 180, 19, 64, 77, 48, 121, 230, 184, 95, 228, 74, 243, 32, 206, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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