Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a8662c2664b05b10cb5c237acf24cbf8480a20d24542d3734abc46847f61f6a

Tx prefix hash: a395f5a1c535545f9b4227cf667b1ee9b6897c56e5a2c01bd876b4fa8f990cb1
Tx public key: fe908f564cf6a6545456b1e5f79e7a3462ad0476a71937958287138b2e21a4ca
Timestamp: 1707334973 Timestamp [UCT]: 2024-02-07 19:42:53 Age [y:d:h:m:s]: 01:070:19:50:42
Block: 952552 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311686 RingCT/type: yes/0
Extra: 01fe908f564cf6a6545456b1e5f79e7a3462ad0476a71937958287138b2e21a4ca02110000000910a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05be9c1bc5b26499bd8d82351e0b058a500d2130d3b1ada016efcb33ba1ab051 0.600000000000 1411594 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": 952562, "vin": [ { "gen": { "height": 952552 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05be9c1bc5b26499bd8d82351e0b058a500d2130d3b1ada016efcb33ba1ab051" } } ], "extra": [ 1, 254, 144, 143, 86, 76, 246, 166, 84, 84, 86, 177, 229, 247, 158, 122, 52, 98, 173, 4, 118, 167, 25, 55, 149, 130, 135, 19, 139, 46, 33, 164, 202, 2, 17, 0, 0, 0, 9, 16, 161, 116, 143, 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