Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5435d2b65cc1bc689a4593c2208ffd5eb565064cdf3c7d00563e908eb5c3069e

Tx prefix hash: 9fa6cdafd32c78efc72d159e2785db39ba0ec0a863d414251b67a38f67f1e44d
Tx public key: 028b2958d265cf1a39d222c878a78fb5d79fc1c4d1c2b979842e6e697bdd4789
Timestamp: 1720051533 Timestamp [UCT]: 2024-07-04 00:05:33 Age [y:d:h:m:s]: 00:272:19:49:41
Block: 1057973 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194932 RingCT/type: yes/0
Extra: 01028b2958d265cf1a39d222c878a78fb5d79fc1c4d1c2b979842e6e697bdd47890211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 82cbace640c6661fdcc8726c6379f0f5e4f1d9bf69d0ff0d7dafbf4e0e6933e2 0.600000000000 1528416 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": 1057983, "vin": [ { "gen": { "height": 1057973 } } ], "vout": [ { "amount": 600000000, "target": { "key": "82cbace640c6661fdcc8726c6379f0f5e4f1d9bf69d0ff0d7dafbf4e0e6933e2" } } ], "extra": [ 1, 2, 139, 41, 88, 210, 101, 207, 26, 57, 210, 34, 200, 120, 167, 143, 181, 215, 159, 193, 196, 209, 194, 185, 121, 132, 46, 110, 105, 123, 221, 71, 137, 2, 17, 0, 0, 0, 2, 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