Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9231fc8d70702bb1cbaff7b8de3ef6c743b3242e3c4bdb73308a82e5a86c3dee

Tx prefix hash: 3adf7e92a75a998d5ef597f583cdaac757d29440fbd2605bf46d6ab57cacb96e
Tx public key: e556e422e8a70461443f753f5771a55521054c5e28da0f0e63715f06f5307a47
Timestamp: 1699065567 Timestamp [UCT]: 2023-11-04 02:39:27 Age [y:d:h:m:s]: 02:018:22:14:56
Block: 884204 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 533111 RingCT/type: yes/0
Extra: 01e556e422e8a70461443f753f5771a55521054c5e28da0f0e63715f06f5307a4702110000000533af99f4000000000000000000

1 output(s) for total of 0.721547795000 dcy

stealth address amount amount idx
00: bd5c2a6759e9b161335941f6577b5385c710e30321eea30243cf340e90f04e61 0.721547795000 1339941 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": 884214, "vin": [ { "gen": { "height": 884204 } } ], "vout": [ { "amount": 721547795, "target": { "key": "bd5c2a6759e9b161335941f6577b5385c710e30321eea30243cf340e90f04e61" } } ], "extra": [ 1, 229, 86, 228, 34, 232, 167, 4, 97, 68, 63, 117, 63, 87, 113, 165, 85, 33, 5, 76, 94, 40, 218, 15, 14, 99, 113, 95, 6, 245, 48, 122, 71, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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