Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc3547d8abe0e38da42ed3c971679a5f687abbc759c0b160af9fbf1ad42e63cb

Tx prefix hash: 7a4d806a914c3e83871eb802391a244a515180507f90c62711fe0775b5f98cfe
Tx public key: 7cef7826819119b422372ea4c9530c3c27b4515e91dac8820c24339f9ce7366d
Timestamp: 1709049077 Timestamp [UCT]: 2024-02-27 15:51:17 Age [y:d:h:m:s]: 00:362:05:01:39
Block: 966780 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258970 RingCT/type: yes/0
Extra: 017cef7826819119b422372ea4c9530c3c27b4515e91dac8820c24339f9ce7366d0211000000090011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc8bb2f3bcb76eb0fb5b9f34e3984b04876501cd29d97b9d14131548a8d401a2 0.600000000000 1426551 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": 966790, "vin": [ { "gen": { "height": 966780 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc8bb2f3bcb76eb0fb5b9f34e3984b04876501cd29d97b9d14131548a8d401a2" } } ], "extra": [ 1, 124, 239, 120, 38, 129, 145, 25, 180, 34, 55, 46, 164, 201, 83, 12, 60, 39, 180, 81, 94, 145, 218, 200, 130, 12, 36, 51, 159, 156, 231, 54, 109, 2, 17, 0, 0, 0, 9, 0, 17, 5, 91, 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