Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49fb436039f171da1a711587f40eb6bdd2eddf6c3cb30b32ff8275a6a85695e0

Tx prefix hash: 6d5d8c8d23fc87f82a1f445d9032fcf0205ae0bf49bd5bc02d414b34a44b3263
Tx public key: 6a554d9f7379e79e6c0c2dc1298c445c447b875e21cbd650e95af1486ca1a6df
Timestamp: 1725108958 Timestamp [UCT]: 2024-08-31 12:55:58 Age [y:d:h:m:s]: 00:130:15:15:24
Block: 1099907 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93441 RingCT/type: yes/0
Extra: 016a554d9f7379e79e6c0c2dc1298c445c447b875e21cbd650e95af1486ca1a6df021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c065d7b210cf55cea0599a288dbea7d1174bf33aaf052db8dfb40e164ca036b3 0.600000000000 1575876 of 15

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": 1099917, "vin": [ { "gen": { "height": 1099907 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c065d7b210cf55cea0599a288dbea7d1174bf33aaf052db8dfb40e164ca036b3" } } ], "extra": [ 1, 106, 85, 77, 159, 115, 121, 231, 158, 108, 12, 45, 193, 41, 140, 68, 92, 68, 123, 135, 94, 33, 203, 214, 80, 233, 90, 241, 72, 108, 161, 166, 223, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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