Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a582c91463522a287eba20dfe33fef0d23cecf3c4db12bd89642845eed30248b

Tx prefix hash: 06fcf8c00d6690399077a1cbe9985590a71a19e641f2cf7e1d1c6ee48c77415a
Tx public key: 1d3e4bbfb5143eaaa6ae0f3ded964a761bae095c9e071c83a9591c03bee2ef21
Timestamp: 1762048948 Timestamp [UCT]: 2025-11-02 02:02:28 Age [y:d:h:m:s]: 00:003:12:06:44
Block: 1403040 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2495 RingCT/type: yes/0
Extra: 011d3e4bbfb5143eaaa6ae0f3ded964a761bae095c9e071c83a9591c03bee2ef210211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b950862d1e0e75c5eede94843b17b5ded23d35ea1814daa949acf8349f94899d 0.600000000000 1891367 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": 1403050, "vin": [ { "gen": { "height": 1403040 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b950862d1e0e75c5eede94843b17b5ded23d35ea1814daa949acf8349f94899d" } } ], "extra": [ 1, 29, 62, 75, 191, 181, 20, 62, 170, 166, 174, 15, 61, 237, 150, 74, 118, 27, 174, 9, 92, 158, 7, 28, 131, 169, 89, 28, 3, 190, 226, 239, 33, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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