Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c6308151d637be0ce147e63734221123fec0e5e1d12cc43fc726a0159bed511

Tx prefix hash: bc83a3f190c63eac09340fc55b1ad7f9e7d632ede52011ea6630608efc86116a
Tx public key: f9058fc53dd102d9a2b3e9b58f5fe44aa46768ae8f59f343cb97d6bc8ba6a5d7
Timestamp: 1618141087 Timestamp [UCT]: 2021-04-11 11:38:07 Age [y:d:h:m:s]: 03:299:14:11:34
Block: 237495 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 974107 RingCT/type: yes/0
Extra: 01f9058fc53dd102d9a2b3e9b58f5fe44aa46768ae8f59f343cb97d6bc8ba6a5d7021100000037b1d898ff000000000000000000

1 output(s) for total of 100.250970564000 dcy

stealth address amount amount idx
00: 0b75a6e2b396417742a4795a733d8e60fcde62bb92814d7e5d9c16e9ebd3b9cb 100.250970564000 494231 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": 237505, "vin": [ { "gen": { "height": 237495 } } ], "vout": [ { "amount": 100250970564, "target": { "key": "0b75a6e2b396417742a4795a733d8e60fcde62bb92814d7e5d9c16e9ebd3b9cb" } } ], "extra": [ 1, 249, 5, 143, 197, 61, 209, 2, 217, 162, 179, 233, 181, 143, 95, 228, 74, 164, 103, 104, 174, 143, 89, 243, 67, 203, 151, 214, 188, 139, 166, 165, 215, 2, 17, 0, 0, 0, 55, 177, 216, 152, 255, 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