Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f366a47877ba35c5c55b16823627131cf60c6c9060deecf68befb164d4f2875

Tx prefix hash: bf01b4958e04fb9e8189785812f350835ace8c653f9ac4110d0af09f6ecf9c3e
Tx public key: 7a96c427ec13b088ba67ec42d2db5d9ca6a8afa82476c7186b3de28b296c6a75
Timestamp: 1764170245 Timestamp [UCT]: 2025-11-26 15:17:25 Age [y:d:h:m:s]: 00:043:04:25:41
Block: 1420618 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30933 RingCT/type: yes/0
Extra: 017a96c427ec13b088ba67ec42d2db5d9ca6a8afa82476c7186b3de28b296c6a750211000000034e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1b5c9c2bde1389ec30adae095d1fc1e3a3779b9f048490bbeb2e77031721c56 0.600000000000 1909167 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": 1420628, "vin": [ { "gen": { "height": 1420618 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1b5c9c2bde1389ec30adae095d1fc1e3a3779b9f048490bbeb2e77031721c56" } } ], "extra": [ 1, 122, 150, 196, 39, 236, 19, 176, 136, 186, 103, 236, 66, 210, 219, 93, 156, 166, 168, 175, 168, 36, 118, 199, 24, 107, 61, 226, 139, 41, 108, 106, 117, 2, 17, 0, 0, 0, 3, 78, 123, 252, 9, 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