Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c3b865029ce9cc82c660091d9de0239044dd44a606f38b2a20d3c85de5286b6

Tx prefix hash: 391594d59a9f1ece9d3836e1189ce7523908903c7184df3d2a461f886f87454b
Tx public key: 241206349fda066de37c72f0cfc85cd0c4c0fe0f8420f4469cab439d4ce7e5c3
Timestamp: 1708690459 Timestamp [UCT]: 2024-02-23 12:14:19 Age [y:d:h:m:s]: 01:045:07:56:34
Block: 963793 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293413 RingCT/type: yes/0
Extra: 01241206349fda066de37c72f0cfc85cd0c4c0fe0f8420f4469cab439d4ce7e5c3021100000003105b1226000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a911f2e57929a9d1885ed423f51e62c603649ff4fa4f43a63cc979e31b4744d 0.600000000000 1423520 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": 963803, "vin": [ { "gen": { "height": 963793 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a911f2e57929a9d1885ed423f51e62c603649ff4fa4f43a63cc979e31b4744d" } } ], "extra": [ 1, 36, 18, 6, 52, 159, 218, 6, 109, 227, 124, 114, 240, 207, 200, 92, 208, 196, 192, 254, 15, 132, 32, 244, 70, 156, 171, 67, 157, 76, 231, 229, 195, 2, 17, 0, 0, 0, 3, 16, 91, 18, 38, 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