Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1443acc6c887977843ebb935b289c998171e4d7f03d62123508d62c46f5778ed

Tx prefix hash: 7dd5853c1e630b12c9db6fba1cb990337d5a490defbefb2d226885fc26998618
Tx public key: e59ac82d2799e8aa6a9728ce96e8c84132e1c9982a8407ae9dcb34d40d127b08
Timestamp: 1764590063 Timestamp [UCT]: 2025-12-01 11:54:23 Age [y:d:h:m:s]: 00:037:19:06:01
Block: 1424098 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 27071 RingCT/type: yes/0
Extra: 01e59ac82d2799e8aa6a9728ce96e8c84132e1c9982a8407ae9dcb34d40d127b08021100000001fb8fd089000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2270ce43f483ccf80e05b87f36c53ab482afcc11b6d8380d99c626ab25059bf 0.600000000000 1912727 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": 1424108, "vin": [ { "gen": { "height": 1424098 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2270ce43f483ccf80e05b87f36c53ab482afcc11b6d8380d99c626ab25059bf" } } ], "extra": [ 1, 229, 154, 200, 45, 39, 153, 232, 170, 106, 151, 40, 206, 150, 232, 200, 65, 50, 225, 201, 152, 42, 132, 7, 174, 157, 203, 52, 212, 13, 18, 123, 8, 2, 17, 0, 0, 0, 1, 251, 143, 208, 137, 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