Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a0fdd55bbe975753038a994ff1c3363a43076b50d67ea61367e3969749b2344

Tx prefix hash: 95b77a038eee3dcad4b74a3321ad77e16ab6bc49b08aa719d781f491afaf8873
Tx public key: 24d3abe45f6d6c1c1e4ae8444333d61d45467b079891c36faab04389ba042beb
Timestamp: 1685477424 Timestamp [UCT]: 2023-05-30 20:10:24 Age [y:d:h:m:s]: 02:009:11:05:45
Block: 771601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 528870 RingCT/type: yes/0
Extra: 0124d3abe45f6d6c1c1e4ae8444333d61d45467b079891c36faab04389ba042beb021100000002e6d27f9c000000000000000000

1 output(s) for total of 1.703592626000 dcy

stealth address amount amount idx
00: 3e756300a90def6d7500e06caaf2cb5fe1869a1fb3cc3ec8c785fa40bdb5b76e 1.703592626000 1220974 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": 771611, "vin": [ { "gen": { "height": 771601 } } ], "vout": [ { "amount": 1703592626, "target": { "key": "3e756300a90def6d7500e06caaf2cb5fe1869a1fb3cc3ec8c785fa40bdb5b76e" } } ], "extra": [ 1, 36, 211, 171, 228, 95, 109, 108, 28, 30, 74, 232, 68, 67, 51, 214, 29, 69, 70, 123, 7, 152, 145, 195, 111, 170, 176, 67, 137, 186, 4, 43, 235, 2, 17, 0, 0, 0, 2, 230, 210, 127, 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