Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae91679556d5bd7b47778076173bd524378349b0314580669909efd7839a0c0c

Tx prefix hash: f406a15c35b3ee479b509b1935d8fbc3f5da95ed0278e65da9504721b4585989
Tx public key: 809c8a519a6f826c4267a0abaf2cb41ddbdfde47f87e76cfa7516de034c12154
Timestamp: 1693998780 Timestamp [UCT]: 2023-09-06 11:13:00 Age [y:d:h:m:s]: 01:016:12:04:02
Block: 842172 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273092 RingCT/type: yes/0
Extra: 01809c8a519a6f826c4267a0abaf2cb41ddbdfde47f87e76cfa7516de034c12154021100000005faf35c9c000000000000000000

1 output(s) for total of 0.994339358000 dcy

stealth address amount amount idx
00: 064d5a50657e5e1802a71a8cc1f922ec1f7cc58e8c9a2040a256075cf8b144ba 0.994339358000 1295266 of 0

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": 842182, "vin": [ { "gen": { "height": 842172 } } ], "vout": [ { "amount": 994339358, "target": { "key": "064d5a50657e5e1802a71a8cc1f922ec1f7cc58e8c9a2040a256075cf8b144ba" } } ], "extra": [ 1, 128, 156, 138, 81, 154, 111, 130, 108, 66, 103, 160, 171, 175, 44, 180, 29, 219, 223, 222, 71, 248, 126, 118, 207, 167, 81, 109, 224, 52, 193, 33, 84, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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