Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f94e6ecc865eae78b4d8ff5d8b9d0138dc08c966b33f6bc541407f58fcda73d3

Tx prefix hash: 24819f9c355e2eca85dfbc64c6755e854327dfbc04bf2c80fec979dcabb93075
Tx public key: 15c4df01b72425ea59ead57b0356c0adce6db009a298653d9ae6125029445c96
Timestamp: 1686027286 Timestamp [UCT]: 2023-06-06 04:54:46 Age [y:d:h:m:s]: 01:313:05:50:06
Block: 776147 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 485076 RingCT/type: yes/0
Extra: 0115c4df01b72425ea59ead57b0356c0adce6db009a298653d9ae6125029445c960211000000014b8f5122000000000000000000

1 output(s) for total of 1.645519222000 dcy

stealth address amount amount idx
00: 16bb2ad1fa9239c139ca5b8bd8a7950a47632261113c97c61c745d6adfa69711 1.645519222000 1225682 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": 776157, "vin": [ { "gen": { "height": 776147 } } ], "vout": [ { "amount": 1645519222, "target": { "key": "16bb2ad1fa9239c139ca5b8bd8a7950a47632261113c97c61c745d6adfa69711" } } ], "extra": [ 1, 21, 196, 223, 1, 183, 36, 37, 234, 89, 234, 213, 123, 3, 86, 192, 173, 206, 109, 176, 9, 162, 152, 101, 61, 154, 230, 18, 80, 41, 68, 92, 150, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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