Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 091810bf48d9fcb84c3e19492f6c1243adeabd268e309902c3463065e8ea35c5

Tx prefix hash: e6f7cdb43644c4377e63f308d517d9ac69f782405f318c5a742c4ab7208c5503
Tx public key: 3eca95a22d0fa34f442127f057798dce4479527ac2faf3775d1dc41e3f808c7d
Timestamp: 1709941701 Timestamp [UCT]: 2024-03-08 23:48:21 Age [y:d:h:m:s]: 01:244:18:22:28
Block: 974176 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 433646 RingCT/type: yes/0
Extra: 013eca95a22d0fa34f442127f057798dce4479527ac2faf3775d1dc41e3f808c7d0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a047c9498a6f4a2ae4ff98f5ba2d42fb47a66df248828e1c813925b19968129 0.600000000000 1434127 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": 974186, "vin": [ { "gen": { "height": 974176 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a047c9498a6f4a2ae4ff98f5ba2d42fb47a66df248828e1c813925b19968129" } } ], "extra": [ 1, 62, 202, 149, 162, 45, 15, 163, 79, 68, 33, 39, 240, 87, 121, 141, 206, 68, 121, 82, 122, 194, 250, 243, 119, 93, 29, 196, 30, 63, 128, 140, 125, 2, 17, 0, 0, 0, 2, 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