Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9dbbf0ab9ffb31ffaa247e4bff1d39269404691e760a965912f174ac77d7998b

Tx prefix hash: 01e68887206a3e995f28fda7935fbc72bce26ab64472710c928356577fb61a9c
Tx public key: 5a4e9f2eb6fddc60882114c479b2fc41d34c96fe731b0c82fe771e430e4c5a60
Timestamp: 1705590455 Timestamp [UCT]: 2024-01-18 15:07:35 Age [y:d:h:m:s]: 01:060:20:24:07
Block: 938076 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304598 RingCT/type: yes/0
Extra: 015a4e9f2eb6fddc60882114c479b2fc41d34c96fe731b0c82fe771e430e4c5a600211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e85380381a49060c0f06fdf0745f96e2b3eaef07fb7d13a7b65992f257f7f2c 0.600000000000 1396140 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": 938086, "vin": [ { "gen": { "height": 938076 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e85380381a49060c0f06fdf0745f96e2b3eaef07fb7d13a7b65992f257f7f2c" } } ], "extra": [ 1, 90, 78, 159, 46, 182, 253, 220, 96, 136, 33, 20, 196, 121, 178, 252, 65, 211, 76, 150, 254, 115, 27, 12, 130, 254, 119, 30, 67, 14, 76, 90, 96, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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