Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f97dcd5a5e6db58d21664a53277f9a9e83d73092d90ba5eb395da80ca656687e

Tx prefix hash: d14afa9a5dc0c31731087f4092e3509365f30d1d08bd6b03e015f90857b37c5d
Tx public key: 4d7782ae9afc27a80e506292cbfe30c6cea18a83711c6bce2e621e3195fe1ab8
Timestamp: 1736342207 Timestamp [UCT]: 2025-01-08 13:16:47 Age [y:d:h:m:s]: 00:160:21:17:11
Block: 1192902 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114687 RingCT/type: yes/0
Extra: 014d7782ae9afc27a80e506292cbfe30c6cea18a83711c6bce2e621e3195fe1ab8021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c312caec2695ab457c9aec34367b2af5daab377b90791731bc83922b67d274bd 0.600000000000 1679459 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": 1192912, "vin": [ { "gen": { "height": 1192902 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c312caec2695ab457c9aec34367b2af5daab377b90791731bc83922b67d274bd" } } ], "extra": [ 1, 77, 119, 130, 174, 154, 252, 39, 168, 14, 80, 98, 146, 203, 254, 48, 198, 206, 161, 138, 131, 113, 28, 107, 206, 46, 98, 30, 49, 149, 254, 26, 184, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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